home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.modems
- Path: news.3do.com!ntg!dplatt
- From: dplatt@ntg.com (Dave Platt)
- Subject: Re: Strange USR Reason Codes for Disconnects
- Message-ID: <1996Jan5.203347.1067@3do.com>
- Sender: news@3do.com (USENET news account)
- Organization: The 3DO Company Inc., Redwood City CA
- References: <4c77c7$qd5@shts.seed.net.tw> <4cai3r$8t2@lurch.sccsi.com> <4cck0p$dao@sol.towson.edu>
- Date: Fri, 5 Jan 1996 20:33:47 GMT
-
- >I have a similar disconnect problem with a USR Mac&Fax sportster
- >connected at 14.4. I'm on a dial-up shell, and the unix box starts
- >displaying a long file (like when I 'cat' a file) , partway thru the file
- >I lose the carrier. I need to know how to figure out why - I would guess
- >either I'm overflowing an input buffer, or there is a character
- >interpreted as 'hangup' which I will need to filter out. It happens when
- >I am just viewing a scroll, or if capturing the screen as it scrolls by.
-
- This can happen if [1] the Mac terminal emulation program is configured
- for "hardware handshaking" or "hardware flow control", and [2] the
- serial port cable connects the Mac's HSKO handshake-output pin to the
- modem's DTR pin (instead of, or as well as to the RTS pin), and [3] the
- modem is configured with &D2 (normal DTR operations).
-
- What happens in this case: if the Mac terminal emulation program can't
- display data as fast as it arrives, the program's serial buffer (and the
- Mac serial-port buffer) fill up. The Mac serial driver turns off the
- HSKO output, to tell the modem to temporarily stop sending data. The
- HSKO output goes to DTR (data terminal ready), and when DTR is
- deasserted and &D2 is specified, the modem "thinks" that you've quit
- from your terminal emulation program, and hangs up the line.
-
- One of the shortcoming of the Mac serial port is that it has only one
- handshake output, which can be used for hangup control (DTR), or receive
- flow control (RTS), but not both at once. Similarly, it has only one
- handshake input, which can be used for either carrier detection (CD) or
- transmit flow control (CTS) but not both (and you have to switch serial
- cables to change the assignment).
-
- In short: if you want to use hardware flow control, you should specify
- AT&D0&H1 (enable hardware flow control on the transmit side, override
- the DTR signal). If you do this, you will NOT be able to hang up the
- modem by quitting from your terminal emulator - you must send the
- pause/+++/pause/ATH0 sequence to force the modem on-hook.
-
- There are two alternatives. One is to use software (XON/XOFF) flow
- control... AT&D2&H0&I2, and specify software flow control in your
- terminal emulator. This has the disadvantage of making it impossible
- for you to transmit XON and XOFF characters through to the system at the
- far end (GNU Emacs users will have difficulties). The other is to use
- no flow control at all (disable receive-data flow control in your
- terminal emulator), and accept overruns if the far end transmits too
- quickly (or use "more" to pace the transmission).
-
-
-
- --
- Dave Platt dplatt@3do.com
- USNAIL: The 3DO Company, Systems Software group
- 600 Galveston Drive
- Redwood City, CA 94063
-